SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Software map</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Software map</span></span>

</h1>

</header>

<div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr"><p>A <b>software map</b> represents static, dynamic, and evolutionary information of <a href="Software_system" title="Software system">software systems</a> and their <a href="Software_development_process" title="Software development process">software development processes</a> by means of 2D or 3D map-oriented <a href="Information_visualization" class="mw-redirect" title="Information visualization">information visualization</a>. It constitutes a fundamental concept and tool in <a href="Software_visualization" title="Software visualization">software visualization</a>, <a href="Software_analytics" title="Software analytics">software analytics</a>, and <a href="Software_diagnosis" title="Software diagnosis">software diagnosis</a>.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> Its primary applications include risk analysis for and monitoring of <a href="Code_quality" class="mw-redirect" title="Code quality">code quality</a>, team activity, or software development progress <sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> and, generally, improving effectiveness of software engineering with respect to all related artifacts, processes, and stakeholders throughout the <a href="Software_engineering" title="Software engineering">software engineering</a> process and <a href="Software_maintenance" title="Software maintenance">software maintenance</a>.

</p>

<div class="mw-heading mw-heading2"><h2 id="Motivation_and_concepts">Motivation and concepts</h2></div>

<p>Software maps are applied in the context of <a href="Software_engineering" title="Software engineering">software engineering</a>: Complex, long-term <a href="Software_development" title="Software development">software development</a> projects are commonly faced by manifold difficulties such as the friction between completing system features and, at the same time, obtaining a high degree of <a href="Code_quality" class="mw-redirect" title="Code quality">code quality</a> and <a href="Software_quality" title="Software quality">software quality</a> to ensure <a href="Software_maintenance" title="Software maintenance">software maintenance</a> of the system in the future. In particular, "Maintaining complex software systems tends to be costly because developers spend a significant part of their time with trying to understand the system’s structure and behavior."<sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> The key idea of software maps is to cope with that challenge and optimization problems by providing effective communication means to close the communication gap among the various stakeholders and information domains within software development projects and obtaining insights in the sense of <a href="Information_visualization" class="mw-redirect" title="Information visualization">information visualization</a>.

</p><p>Software maps take advantage of well-defined cartographic <a href="Map" title="Map">map</a> techniques using the virtual <a href="3D_city_models" class="mw-redirect" title="3D city models">3D city model</a> metaphor<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> to express the underlying complex, abstract information space. The metaphor is required "since software has no physical shape, there is no natural mapping of software to a two-dimensional space".<sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup> Software maps are non-spatial <a href="Map" title="Map">maps</a> that have to convert the hierarchy data and its attributes into a spatial representation.

</p>

<div class="mw-heading mw-heading2"><h2 id="Applications">Applications</h2></div>

<p>Software maps generally allow for comprehensible and effective communication of course, risks, and costs of software development projects to various stakeholders such as management and development teams. They communicate the status of applications and systems currently being developed or further developed to project leaders and management at a glance. "A key aspect for this decision-making is that software maps provide the structural context required for correct interpretation of these performance indicators".<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup> As an instrument of communication, software maps act as open, transparent information spaces which enable priorities of code quality and the creation of new functions to be balanced against one another and to decide upon and implement necessary measures to improve the <a href="Software_development_process" title="Software development process">software development process</a>.

</p><p>For example, they facilitate decisions as to where in the code an increase in quality would be beneficial both for speeding up current development activities and for reducing risks of future maintenance problems.

</p><p>Due to their high degree of expressiveness (e.g., information density) and their instantaneous, automated generation, the maps additionally serve to reflect the current status of system and development processes, bridging an essential information gap between management and development teams, improve awareness about the status, and serve as early risk detection instrument.

</p>

<div class="mw-heading mw-heading2"><h2 id="Contents">Contents</h2></div>

<p>Software maps are based on objective information as determined by the <a href="KPI_driven_code_analysis" class="mw-redirect" title="KPI driven code analysis">KPI driven code analysis</a> as well as by imported information from <a href="Software_repository" title="Software repository">software repository</a> systems, information from the <a href="Source_code" title="Source code">source codes</a>, or <a href="Software_development_tool" class="mw-redirect" title="Software development tool">software development tools</a> and <a href="Programming_tool" title="Programming tool">programming tools</a>. In particular, software maps are not bound to a specific <a href="Programming_language" title="Programming language">programming language</a>, <a href="Modeling_language" title="Modeling language">modeling language</a>, or <a href="Software_development_process" title="Software development process">software development process</a> model.

</p><p>Software maps use the hierarchy of the software implementation artifacts such as <a href="Source_code" title="Source code">source code</a> files as a base to build a <a href="Tree_mapping" class="mw-redirect" title="Tree mapping">tree mapping</a>, i.e., a rectangular area that represents the whole hierarchy, subdividing the area into rectangular sub-areas. A software map, informally speaking, looks similar to a virtual <a href="3D_city_model" title="3D city model">3D city model</a>, whereby artifacts of the software system appear as virtual, rectangular 3D buildings or towers, which are placed according to their position in the software implementation hierarchy.

</p><p>Software maps can express and combine information about software development, software quality, and <a href="System_dynamics" title="System dynamics">system dynamics</a> by mapping that information onto visual variables<sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> of the tree map elements such as footprint size, height, color or texture. They can systematically be specified, automatically generated, and organized by templates.

</p>

<div class="mw-heading mw-heading2"><h2 id="Mapping_software_system_example">Mapping software system example</h2></div>

<p>Software maps "combine thematic information about software development processes (evolution), software quality, structure, and dynamics and display that information in a cartographic manner".<sup id="cite_ref-Trümper12_8-0" class="reference"><a href="#cite_note-Trümper12-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> For example:

</p>

<ul><li>The height of a virtual building can be proportional to the complexity of the code unit (e.g., single or combined <a href="Software_metric" title="Software metric">software metrics</a>).</li>

<li>The ground area of a virtual 3D building can be proportional to the number of lines of code in the module or (e.g., non-comment lines-of-code NCLOC).</li>

<li>The color can express the current development status, i.e., how many developers are changing/editing the code unit.</li></ul>

<p>With this exemplary configuration, the software map shows crucial points in the source code with relations to aspects of the software development process. For example, it becomes obvious at a glance what to change in order to:

</p>

<ul><li>implement changes quickly;</li>

<li>evaluate quickly the impact of changes in one place on functionality elsewhere;</li>

<li>reduce entanglements that lead to uncontrolled processes in the application;</li>

<li>find errors faster;</li>

<li>discover and eliminate bad programming style.</li></ul>

<p>Software maps represent key tools in the scope of automated software diagnosis <a rel="nofollow" class="external text" href="http://www.softwarediagnostics.com">software diagnostics</a>.

</p>

<div class="mw-heading mw-heading2"><h2 id="As_business_intelligence_tools_and_recommendation_systems">As business intelligence tools and recommendation systems</h2></div>

<p>Software maps can be used, in particular, as analysis and presentation tool of <a href="Business_intelligence" title="Business intelligence">business intelligence</a> systems, specialized in the analysis of software related data. Furthermore, software maps "serve as recommendation systems for software engineering".<sup id="cite_ref-Trümper12_8-1" class="reference"><a href="#cite_note-Trümper12-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup>

</p><p>Software maps are not limited by software-related information: They can include any hierarchical system information as well, for example, maintenance information about complex technical artifacts.

</p>

<div class="mw-heading mw-heading2"><h2 id="Visualization_techniques">Visualization techniques</h2></div>

<p>Software maps are investigated in the domain of <a href="Software_visualization" title="Software visualization">software visualization</a>. The visualization of software maps is commonly based on <a href="Tree_mapping" class="mw-redirect" title="Tree mapping">tree mapping</a>, "a space-filling approach to the visualization of hierarchical information structures"<sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup> or other hierarchy mapping approaches.

</p>

<div class="mw-heading mw-heading3"><h3 id="Layout_algorithms">Layout algorithms</h3></div>

<p>To construct software maps, different layout approaches are used to generate the basic spatial mapping of components, such as:

</p>

<ul><li>Tree-map algorithms that initially map the software hierarchy into a recursively nested rectangular area.</li>

<li>Voronoi-map algorithms that initially map the software hierarchy by generating a <a href="Voronoi_diagram" title="Voronoi diagram">Voronoi</a> map.</li></ul>

<div class="mw-heading mw-heading3"><h3 id="Layout_stability">Layout stability</h3></div>

<p>The spatial arrangement computed by layouts such as defined by tree maps strictly depends on the hierarchy. If software maps have to be generated frequently for an evolving or changing system, the usability of software maps is affected by non-stable layouts, that is, minor changes to the hierarchy may cause significant changes to the layout.

</p><p>In contrast to regular Voronoi treemap algorithms, which do not provide deterministic layouts, the layout algorithm for Voronoi treemaps can be extended to provides a high degree of layout similarity for varying hierarchies.<sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup> Similar approaches exist for the tree-map based case.

</p>

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

<p>Software maps methods and techniques belong to the scientific discipline of <a href="Software_visualization" title="Software visualization">software visualization</a> and <a href="Information_visualization" class="mw-redirect" title="Information visualization">information visualization</a>. They form a key concept and technique within the fields of <a href="Software_diagnosis" title="Software diagnosis">software diagnosis</a>. They also have applications in <a href="Software_mining" title="Software mining">software mining</a> and <a href="Software_analytics" title="Software analytics">software analytics</a>. Software maps have been extensively developed and researched by, e.g., at the <a href="Hasso_Plattner_Institute" title="Hasso Plattner Institute">Hasso Plattner Institute</a> for IT systems engineering, in particular for large-scale, complex IT systems and applications.

</p>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFDiehl2007" class="citation book cs1">Diehl, Stephan (2007). <i>Software visualization : visualizing the structure, behaviour, and evolution of software</i>. Berlin: Springer. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-3-540-46505-8</bdi>. <a href="OCLC_(identifier)" class="mw-redirect" title="OCLC (identifier)">OCLC</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/oclc/184984646">184984646</a>.</cite></span>

</li>

<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text"><cite id="CITEREFBohnetDöllner2011" class="citation book cs1">Bohnet, J.; Döllner, J. (2011). <a rel="nofollow" class="external text" href="https://www.researchgate.net/publication/241622611">"Monitoring Code Quality and Development Activity by Software Maps"</a>. <i>Proceedings of the IEEE ACM ICSE Workshop on Managing Technical Debt</i>. Association for Computing Machinery. pp. <span class="nowrap">9–</span>16. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F1985362.1985365">10.1145/1985362.1985365</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781450305860</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:17258620">17258620</a>.</cite></span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text"><cite id="CITEREFBohnet2010" class="citation thesis cs1">Bohnet, J. (2010). <a rel="nofollow" class="external text" href="https://publishup.uni-potsdam.de/opus4-ubp/frontdoor/index/index/docId/32254"><i>Visualization of Execution Traces and its Application to Software Maintenance</i></a> (PhD). Hasso-Plattner-Institut, University of Potsdam.</cite></span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text"><cite id="CITEREFWettelLanza2007" class="citation book cs1">Wettel, R.; Lanza, M. (2007). "Visualizing Software Systems as Cities". <i>Proceedings of VISSOFT 2007 (4th IEEE International Workshop on Visualizing Software For Understanding and Analysis)</i>. IEEE Computer Society Press. pp. <span class="nowrap">92–</span>99. <a href="CiteSeerX_(identifier)" class="mw-redirect" title="CiteSeerX (identifier)">CiteSeerX</a> <span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.135.1979">10.1.1.135.1979</a></span>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FVISSOF.2007.4290706">10.1109/VISSOF.2007.4290706</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4244-0599-2</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:9974947">9974947</a>.</cite></span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><cite id="CITEREFKuhnLoretanNierstrasz2008" class="citation book cs1">Kuhn, A.; Loretan, P.; Nierstrasz, O. (2008). "Consistent Layout for Thematic Software Maps". <i>2008 15th Working Conference on Reverse Engineering</i>. pp. <span class="nowrap">209–</span>218. <a href="ArXiv_(identifier)" class="mw-redirect" title="ArXiv (identifier)">arXiv</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://arxiv.org/abs/1209.5490">1209.5490</a></span>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FWCRE.2008.45">10.1109/WCRE.2008.45</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-7695-3429-9</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:232783">232783</a>.</cite></span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><cite id="CITEREFLimbergerWastyTrümperDöllner2013" class="citation book cs1">Limberger, D.; Wasty, B.; Trümper, J.; Döllner, J. (2013). "Interactive software maps for web-based source code analysis". <i>Proceedings of the 18th International Conference on 3D Web Technology</i>. pp. <span class="nowrap">91–</span>98. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F2466533.2466550">10.1145/2466533.2466550</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781450321334</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:3040005">3040005</a>.</cite></span>

</li>

<li id="cite_note-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-7">^</a></b></span> <span class="reference-text"><cite id="CITEREFCarpendale" class="citation web cs1">Carpendale, M.S.T. <a rel="nofollow" class="external text" href="http://innovis.cpsc.ucalgary.ca/innovis/uploads/Publications/Publications/Carpendale_visual_variables.pdf">"Considering Visual Variables as a Basis for Information Visualization"</a> <span class="cs1-format">(PDF)</span>.</cite></span>

</li>

<li id="cite_note-Trümper12-8"><span class="mw-cite-backlink">^ <a href="#cite_ref-Trümper12_8-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Trümper12_8-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFTrümperDöllner2012" class="citation book cs1">Trümper, Jonas; Döllner, Jürgen (2012). "Extending Recommendation Systems with Software Maps". <i>Proceedings of the 3rd International ICSE Workshop on Recommendation Systems for Software Engineering (RSSE)</i>. IEEE Computer Society. pp. <span class="nowrap">92–</span>96. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FRSSE.2012.6233420">10.1109/RSSE.2012.6233420</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4673-1758-0</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:1609575">1609575</a>.</cite></span>

</li>

<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text"><cite id="CITEREFJohnsonShneiderman1991" class="citation book cs1">Johnson, B.; Shneiderman, B. (1991). <a rel="nofollow" class="external text" href="https://drum.lib.umd.edu/bitstream/handle/1903/370/CS-TR-2657.pdf?sequence=2&isAllowed=y">"Tree-maps: a space-filling approach to the visualization of hierarchical information structures"</a> <span class="cs1-format">(PDF)</span>. <i>Proceeding Visualization '91</i>. pp. <span class="nowrap">284–</span>291. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FVISUAL.1991.175815">10.1109/VISUAL.1991.175815</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-8186-2245-8</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:1733343">1733343</a>.</cite></span>

</li>

<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text"><cite id="CITEREFHahnTrümperMoritzDöllner2014" class="citation book cs1">Hahn, S.; Trümper, J.; Moritz, D.; Döllner, J. (2014). <a rel="nofollow" class="external text" href="https://www.researchgate.net/publication/259752051">"Visualization of varying hierarchies by stable layout of voronoi treemaps"</a>. <i>2014 International Conference on Information Visualization Theory and Applications (IVAPP)</i>. pp. <span class="nowrap">50–</span>58. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-9-8975-8132-8</bdi>.</cite></span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li>Scientific conference VISSOFT (IEEE Working Conference on Software Visualization) <a rel="nofollow" class="external autonumber" href="http://vissoft.iro.umontreal.ca">[1]</a></li>

<li><a rel="nofollow" class="external text" href="http://www.hpi.uni-potsdam.de/doellner/publications/year/2013/2193/TSD2013.html">Interactive Rendering of Complex 3D-Treemaps</a></li>

<li><a rel="nofollow" class="external text" href="http://www.hpi.uni-potsdam.de/doellner/publications/year/2013/2272/TDT2013.html">Multiscale Visual Comparison of Execution Traces</a></li>

<li><a rel="nofollow" class="external text" href="http://www.hpi.uni-potsdam.de/doellner/publications/year/2013/2275/LWTD2013.html">Interactive Software Maps for Web-Based Source Code Analysis</a></li>

<li><a rel="nofollow" class="external text" href="http://www.hpi.uni-potsdam.de/doellner/publications/year/2012/2076/TD2012.html">Extending Recommendation Systems with Software Maps</a></li>

<li><a rel="nofollow" class="external text" href="http://www.hpi.uni-potsdam.de/doellner/publications/year/2012/2113/TBD2012.html">A Visual Analysis Approach to Support Perfective Software Maintenance</a></li>

<li><a rel="nofollow" class="external text" href="http://www.hpi.uni-potsdam.de/doellner/publications/year/2012/2126/TTD2012.html">ViewFusion: Correlating Structure and Activity Views for Execution Traces</a></li>

<li><a rel="nofollow" class="external text" href="http://www.hpi.uni-potsdam.de/doellner/publications/year/2011/2071/BTD2011.html">A Visual Analysis and Design Tool for Planning Software Reengineerings</a></li>

<li><a rel="nofollow" class="external text" href="http://www.hpi.uni-potsdam.de/doellner/publications/year/2011/2033/LTD2011.html">Interactive Areal Annotations for 3D Treemaps of Large-Scale Software Systems</a></li>

<li><a rel="nofollow" class="external text" href="http://www.hpi.uni-potsdam.de/doellner/publications/year/2011/2048/BOH11.html">Visualization of Execution Traces and its Application to Software Maintenance</a></li>

<li><a rel="nofollow" class="external text" href="http://www.hpi.uni-potsdam.de/doellner/publications/year/2010/1219/TBD10.html">Understanding Complex Multithreaded Software Systems by Using Trace Visualization</a></li>

<li><a rel="nofollow" class="external text" href="http://www.hpi.uni-potsdam.de/doellner/publications/year/2010/1218/TBVD10.html">Visualization of Multithreaded Behavior to Facilitate Maintenance of Complex Software Systems</a></li>

<li><a rel="nofollow" class="external text" href="http://www.hpi.uni-potsdam.de/doellner/publications/year/2009/812/BKD09.html">Visualizing Massively Pruned Execution Traces to Facilitate Trace Exploration</a></li>

<li><a rel="nofollow" class="external text" href="http://www.hpi.uni-potsdam.de/doellner/publications/year/2009/825/BVD09.html">Projecting Code Changes onto Execution Traces to Support Localization of Recently Introduced Bugs</a></li>

<li><a rel="nofollow" class="external text" href="http://www.hpi.uni-potsdam.de/doellner/publications/year/2013/2284/KTD2013.html">SyncTrace: Visual Thread-Interplay Analysis</a></li></ul></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-07-19" href="https://en.wikipedia.org/wiki/?title=Software_map&oldid=1301306033">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>